Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e14318f6cad12a214d3bd91a8cd770c74e740b0eefa7de12d83bbf8eb7fea8b

Tx prefix hash: 9c4099ed788446b38ec46c2a6dfe1a3ed5b01ffc59e194f2a31ffc6b38e79f77
Tx public key: b385d0a1b959a889e6820f7067578290d2e5a2f0d7562d7c3de90d586b1a3a66
Timestamp: 1739243784 Timestamp [UCT]: 2025-02-11 03:16:24 Age [y:d:h:m:s]: 00:320:01:35:07
Block: 1216659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226566 RingCT/type: yes/0
Extra: 01b385d0a1b959a889e6820f7067578290d2e5a2f0d7562d7c3de90d586b1a3a660211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc98f8d1e0490e962bc06081ad00d8cb9b94422feccb8f830283f587a6e3d3c3 0.600000000000 1703466 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": 1216669, "vin": [ { "gen": { "height": 1216659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc98f8d1e0490e962bc06081ad00d8cb9b94422feccb8f830283f587a6e3d3c3" } } ], "extra": [ 1, 179, 133, 208, 161, 185, 89, 168, 137, 230, 130, 15, 112, 103, 87, 130, 144, 210, 229, 162, 240, 215, 86, 45, 124, 61, 233, 13, 88, 107, 26, 58, 102, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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