Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b72ddbb31baf64778450b5e43f80ac2b47d81bc26f9daab8ef09aef99febca7

Tx prefix hash: 5762f55529609d0d4514a5e0fcbc43c6a2790cacea6042e1fca340f2679dad9c
Tx public key: 00ec6f3e53e5440648e9c98bb5fc5b880f9cb9677c6001a7fab572aa9f7f8e18
Timestamp: 1723009978 Timestamp [UCT]: 2024-08-07 05:52:58 Age [y:d:h:m:s]: 00:245:11:55:50
Block: 1082506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175352 RingCT/type: yes/0
Extra: 0100ec6f3e53e5440648e9c98bb5fc5b880f9cb9677c6001a7fab572aa9f7f8e1802110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07e46c9e7466c97694ba75cc29aaace2c017bf144c292b275633ce9497d883ac 0.600000000000 1556335 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": 1082516, "vin": [ { "gen": { "height": 1082506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07e46c9e7466c97694ba75cc29aaace2c017bf144c292b275633ce9497d883ac" } } ], "extra": [ 1, 0, 236, 111, 62, 83, 229, 68, 6, 72, 233, 201, 139, 181, 252, 91, 136, 15, 156, 185, 103, 124, 96, 1, 167, 250, 181, 114, 170, 159, 127, 142, 24, 2, 17, 0, 0, 0, 6, 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