Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aea6f5a78a5c7740d2f3eb1fc7de34f045ca71608521216c191d941d88aaba62

Tx prefix hash: 82f975c5432d2057828e47503127f3995f3bf72a5009f2369e5345bc6c5095cd
Tx public key: 6539d54d03e26c96e203a606d9b29caa7d18abe824d5d762940f2715166eaebb
Timestamp: 1730155939 Timestamp [UCT]: 2024-10-28 22:52:19 Age [y:d:h:m:s]: 00:084:08:28:45
Block: 1141694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60289 RingCT/type: yes/0
Extra: 016539d54d03e26c96e203a606d9b29caa7d18abe824d5d762940f2715166eaebb021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f776cf4a9c4971a2b192c761cb96169c8f4fff7d886e61cd5537fd7cd881c0f0 0.600000000000 1625505 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": 1141704, "vin": [ { "gen": { "height": 1141694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f776cf4a9c4971a2b192c761cb96169c8f4fff7d886e61cd5537fd7cd881c0f0" } } ], "extra": [ 1, 101, 57, 213, 77, 3, 226, 108, 150, 226, 3, 166, 6, 217, 178, 156, 170, 125, 24, 171, 232, 36, 213, 215, 98, 148, 15, 39, 21, 22, 110, 174, 187, 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