Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b9bb243e7c789ad53baf4cdbf658de0e59e0fe996473a9ec498f508e56fa8ef

Tx prefix hash: e8b58ea82dd2db1f562cdf20110f76db529e23c406cd9edac4d7a4058cbde3ee
Tx public key: cbe90e425eb6fa8c28682a8effca8c461c87df13d27b59eaf01b931045eeba5e
Timestamp: 1705594636 Timestamp [UCT]: 2024-01-18 16:17:16 Age [y:d:h:m:s]: 01:082:08:35:16
Block: 938113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319954 RingCT/type: yes/0
Extra: 01cbe90e425eb6fa8c28682a8effca8c461c87df13d27b59eaf01b931045eeba5e0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35278d83ca2daf1bda16f75e613db4ce0e02b7f519b34c510645b08f7c94393e 0.600000000000 1396179 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": 938123, "vin": [ { "gen": { "height": 938113 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35278d83ca2daf1bda16f75e613db4ce0e02b7f519b34c510645b08f7c94393e" } } ], "extra": [ 1, 203, 233, 14, 66, 94, 182, 250, 140, 40, 104, 42, 142, 255, 202, 140, 70, 28, 135, 223, 19, 210, 123, 89, 234, 240, 27, 147, 16, 69, 238, 186, 94, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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