Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 858792d1cab1f1ecb12e9fa5f24f7effbc28f03380393a1ec41e9725a7065e48

Tx prefix hash: 3ed9d29c28d4a77afa9ee3ce4480c815adb8d761e049def918bfcad1fdf3f4ef
Tx public key: 209dcf8b068a7ba5c4a021df81d1921c763ef48bb20f86c6f1d48f5468d10045
Timestamp: 1689510150 Timestamp [UCT]: 2023-07-16 12:22:30 Age [y:d:h:m:s]: 01:300:01:58:59
Block: 805041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 475606 RingCT/type: yes/0
Extra: 01209dcf8b068a7ba5c4a021df81d1921c763ef48bb20f86c6f1d48f5468d1004502110000000475e3f0e9000000000000000000

1 output(s) for total of 1.319973162000 dcy

stealth address amount amount idx
00: 391ee53287108f8e1533a2a4118afd6dfe13eaccc134da08cf208e8c754627e5 1.319973162000 1256260 of 0

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": 805051, "vin": [ { "gen": { "height": 805041 } } ], "vout": [ { "amount": 1319973162, "target": { "key": "391ee53287108f8e1533a2a4118afd6dfe13eaccc134da08cf208e8c754627e5" } } ], "extra": [ 1, 32, 157, 207, 139, 6, 138, 123, 165, 196, 160, 33, 223, 129, 209, 146, 28, 118, 62, 244, 139, 178, 15, 134, 198, 241, 212, 143, 84, 104, 209, 0, 69, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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