Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3908db0de6df83afc2b01108f8efdf5399c50b66f96f107796cfb851b0000c9

Tx prefix hash: 766482f20cbf4922a2f3c63d69a691abb8dbebc85aaaec6dbe5175b19c89cc29
Tx public key: bbcf314ec47600786074b6cb0ff0efa49ed2db44e69d7a582680c1d377dd3f9d
Timestamp: 1725356694 Timestamp [UCT]: 2024-09-03 09:44:54 Age [y:d:h:m:s]: 00:214:12:44:22
Block: 1101972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153160 RingCT/type: yes/0
Extra: 01bbcf314ec47600786074b6cb0ff0efa49ed2db44e69d7a582680c1d377dd3f9d02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26ba5c2c57d9e0da69d6e7e72130894729458ea18839f5e2392edb992a66f011 0.600000000000 1578227 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": 1101982, "vin": [ { "gen": { "height": 1101972 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26ba5c2c57d9e0da69d6e7e72130894729458ea18839f5e2392edb992a66f011" } } ], "extra": [ 1, 187, 207, 49, 78, 196, 118, 0, 120, 96, 116, 182, 203, 15, 240, 239, 164, 158, 210, 219, 68, 230, 157, 122, 88, 38, 128, 193, 211, 119, 221, 63, 157, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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