Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be16d21349495283bf3150ddc6242165b97862b70cde371318fba682cb6e2833

Tx prefix hash: 046e85075d905d20448160ffe54bb2d477f1752e58c84f93f24d1a0632801c7c
Tx public key: 46a7b806c308c2d7a307c6bb13cfedee279ce3f05ffc9e1a9e378606d654aa4d
Timestamp: 1739012868 Timestamp [UCT]: 2025-02-08 11:07:48 Age [y:d:h:m:s]: 00:333:05:12:49
Block: 1214749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235983 RingCT/type: yes/0
Extra: 0146a7b806c308c2d7a307c6bb13cfedee279ce3f05ffc9e1a9e378606d654aa4d021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5987551db3633d9ca7c63f51e4a94c50ca8ad50b439f3478fec2f1841d551f2 0.600000000000 1701544 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": 1214759, "vin": [ { "gen": { "height": 1214749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5987551db3633d9ca7c63f51e4a94c50ca8ad50b439f3478fec2f1841d551f2" } } ], "extra": [ 1, 70, 167, 184, 6, 195, 8, 194, 215, 163, 7, 198, 187, 19, 207, 237, 238, 39, 156, 227, 240, 95, 252, 158, 26, 158, 55, 134, 6, 214, 84, 170, 77, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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