Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 161a6b13427d1eed370e9665a97ecdc2eb0dfe4a17663dc670913b8e630fe883

Tx prefix hash: 2e7e2ec6ff1713d1d32f1cec1df578389cb085c3fb1caaf38cf8120044c3f3e0
Tx public key: b57344aaaf6369fde0f01ae007ed147e2e5759ab21f1b716755a0cde8510f04e
Timestamp: 1728125631 Timestamp [UCT]: 2024-10-05 10:53:51 Age [y:d:h:m:s]: 00:238:04:25:17
Block: 1124923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170080 RingCT/type: yes/0
Extra: 01b57344aaaf6369fde0f01ae007ed147e2e5759ab21f1b716755a0cde8510f04e02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5615ba587f0ef190509f65f3abd2fadf18a340fa85d0d35753ba85558d6b474 0.600000000000 1607596 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": 1124933, "vin": [ { "gen": { "height": 1124923 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5615ba587f0ef190509f65f3abd2fadf18a340fa85d0d35753ba85558d6b474" } } ], "extra": [ 1, 181, 115, 68, 170, 175, 99, 105, 253, 224, 240, 26, 224, 7, 237, 20, 126, 46, 87, 89, 171, 33, 241, 183, 22, 117, 90, 12, 222, 133, 16, 240, 78, 2, 17, 0, 0, 0, 2, 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