Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60efc17f99c4d7543d26783233cad82e644226b70032eee5f5fc9a16a0fe35ba

Tx prefix hash: 47fba1d3231e1786797758666f675be92fd8f8126a125bb6c5f8227845e9afd6
Tx public key: 1929f0e1c877c3e4dc3c337900850c74714d3d95002d92e9b6a1f1e52637a0c1
Timestamp: 1724896659 Timestamp [UCT]: 2024-08-29 01:57:39 Age [y:d:h:m:s]: 00:289:02:22:57
Block: 1098151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206440 RingCT/type: yes/0
Extra: 011929f0e1c877c3e4dc3c337900850c74714d3d95002d92e9b6a1f1e52637a0c102110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0b3f5c56232b9b7c4ebf7bc08d85feee7d46cbb2146e96485a895423f8ec3f1 0.600000000000 1573766 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": 1098161, "vin": [ { "gen": { "height": 1098151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0b3f5c56232b9b7c4ebf7bc08d85feee7d46cbb2146e96485a895423f8ec3f1" } } ], "extra": [ 1, 25, 41, 240, 225, 200, 119, 195, 228, 220, 60, 51, 121, 0, 133, 12, 116, 113, 77, 61, 149, 0, 45, 146, 233, 182, 161, 241, 229, 38, 55, 160, 193, 2, 17, 0, 0, 0, 3, 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