Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f56d318e57b845e6b96be77166209644c8316a6f1d515fb7150882f2721f6c1

Tx prefix hash: 0595437daa65f7883a881162c30ee7dbc576d0d769b2c764c9639b410006cd06
Tx public key: cc46dad9e14b06e3e2acff2903c8616673bd4621b262d1e763e08f4d916fb04b
Timestamp: 1734144087 Timestamp [UCT]: 2024-12-14 02:41:27 Age [y:d:h:m:s]: 00:108:23:08:04
Block: 1174725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77637 RingCT/type: yes/0
Extra: 01cc46dad9e14b06e3e2acff2903c8616673bd4621b262d1e763e08f4d916fb04b0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 614937ca45e9ea7c194ddb94ba131940e0dfcde6d75bff03670d89f64f52affd 0.600000000000 1660914 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": 1174735, "vin": [ { "gen": { "height": 1174725 } } ], "vout": [ { "amount": 600000000, "target": { "key": "614937ca45e9ea7c194ddb94ba131940e0dfcde6d75bff03670d89f64f52affd" } } ], "extra": [ 1, 204, 70, 218, 217, 225, 75, 6, 227, 226, 172, 255, 41, 3, 200, 97, 102, 115, 189, 70, 33, 178, 98, 209, 231, 99, 224, 143, 77, 145, 111, 176, 75, 2, 17, 0, 0, 0, 2, 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