Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae8ad9fb164be2fa7eafbdae1b3d00f1df8ebaf629546b09760c53fdb00b6c8f

Tx prefix hash: b74f4c042c6bc3254b8003525bccddedc05da832c1a86ab01cf66ff1053061c9
Tx public key: 484a44c64370fbd28a97372ab0c7f2bb4cccb52c0d0093387f2c63264aea0667
Timestamp: 1714731356 Timestamp [UCT]: 2024-05-03 10:15:56 Age [y:d:h:m:s]: 00:331:23:35:38
Block: 1013878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237300 RingCT/type: yes/0
Extra: 01484a44c64370fbd28a97372ab0c7f2bb4cccb52c0d0093387f2c63264aea06670211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68b8a02973d4375f7c34e2e317fda92e1510c62cca7074a4eae5e75aee0800ab 0.600000000000 1476811 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": 1013888, "vin": [ { "gen": { "height": 1013878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68b8a02973d4375f7c34e2e317fda92e1510c62cca7074a4eae5e75aee0800ab" } } ], "extra": [ 1, 72, 74, 68, 198, 67, 112, 251, 210, 138, 151, 55, 42, 176, 199, 242, 187, 76, 204, 181, 44, 13, 0, 147, 56, 127, 44, 99, 38, 74, 234, 6, 103, 2, 17, 0, 0, 0, 2, 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