Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f726e1705f66e2934d13803bcaec3fd1505c184ceadac653425767c9c556744

Tx prefix hash: 47805c54f7944d6eb46cccd383e4d9a75a91f3da5dad57002ba08e90320967ea
Tx public key: 9610e9aa96cad24335eb16bdc79cceba8a10ec8c0464a37f3f1e1496c0fc0b9b
Timestamp: 1718539505 Timestamp [UCT]: 2024-06-16 12:05:05 Age [y:d:h:m:s]: 00:333:13:03:12
Block: 1045461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238363 RingCT/type: yes/0
Extra: 019610e9aa96cad24335eb16bdc79cceba8a10ec8c0464a37f3f1e1496c0fc0b9b02110000000136ea7c8b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c70cba6df4c2277712b82f5d1ad2c3ffda73ed3b549e5bec9c05119134e1c67 0.600000000000 1515040 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": 1045471, "vin": [ { "gen": { "height": 1045461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c70cba6df4c2277712b82f5d1ad2c3ffda73ed3b549e5bec9c05119134e1c67" } } ], "extra": [ 1, 150, 16, 233, 170, 150, 202, 210, 67, 53, 235, 22, 189, 199, 156, 206, 186, 138, 16, 236, 140, 4, 100, 163, 127, 63, 30, 20, 150, 192, 252, 11, 155, 2, 17, 0, 0, 0, 1, 54, 234, 124, 139, 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