Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b1c993ddb698c7b925b0ef6a8bdf06b37135b9ae0fc5c9377176dd2b8d9362b

Tx prefix hash: 61aa7c6211cc62676c89464883be7608d85f31787c4085cdeebe9c34bc919cb2
Tx public key: e3abd5f4c2c65ec399fdcbce7001f4727e93bdf240f0cf36258f3392c9886537
Timestamp: 1732144649 Timestamp [UCT]: 2024-11-20 23:17:29 Age [y:d:h:m:s]: 00:124:15:58:54
Block: 1158137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88914 RingCT/type: yes/0
Extra: 01e3abd5f4c2c65ec399fdcbce7001f4727e93bdf240f0cf36258f3392c98865370211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e310a108d0ddce578d81b6a15443e21df4fcb0dbb0c03c8c50eec701ed1f4304 0.600000000000 1643766 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": 1158147, "vin": [ { "gen": { "height": 1158137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e310a108d0ddce578d81b6a15443e21df4fcb0dbb0c03c8c50eec701ed1f4304" } } ], "extra": [ 1, 227, 171, 213, 244, 194, 198, 94, 195, 153, 253, 203, 206, 112, 1, 244, 114, 126, 147, 189, 242, 64, 240, 207, 54, 37, 143, 51, 146, 201, 136, 101, 55, 2, 17, 0, 0, 0, 3, 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