Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 40a05090545a9d1e57c8e06c196efb829b4e950731950753f743d855e5963681

Tx prefix hash: 485ca547737fb4c1936cd09b213488273ae5f1ef4411ded721ac042eb8fc00d1
Tx public key: be49af54d0356cc1bfda30c6fe1f2fe8d4fd38ecfdf545b130e9708a71a904ee
Timestamp: 1714462140 Timestamp [UCT]: 2024-04-30 07:29:00 Age [y:d:h:m:s]: 01:029:20:37:04
Block: 1011641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282301 RingCT/type: yes/0
Extra: 01be49af54d0356cc1bfda30c6fe1f2fe8d4fd38ecfdf545b130e9708a71a904ee0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1dad6a1205b93e2791a0b09dfac6e7e2a3c93cd3c5792fe85a3cdebf84aec8ff 0.600000000000 1473923 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1011651, "vin": [ { "gen": { "height": 1011641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1dad6a1205b93e2791a0b09dfac6e7e2a3c93cd3c5792fe85a3cdebf84aec8ff" } } ], "extra": [ 1, 190, 73, 175, 84, 208, 53, 108, 193, 191, 218, 48, 198, 254, 31, 47, 232, 212, 253, 56, 236, 253, 245, 69, 177, 48, 233, 112, 138, 113, 169, 4, 238, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8