Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09d122e6327d835ba5a05144dd55b2d18d89de7912a8b782ffef2b7c222a3930

Tx prefix hash: 3df84c6416f10c1c24acfef4c0e4925b948141e231dc00c8ba2542bc799fda60
Tx public key: 8893a0f51919d9a0690183f015c93f31847039f1d7a6e5467d773de16be310f8
Timestamp: 1715376273 Timestamp [UCT]: 2024-05-10 21:24:33 Age [y:d:h:m:s]: 00:350:10:17:00
Block: 1019239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250481 RingCT/type: yes/0
Extra: 018893a0f51919d9a0690183f015c93f31847039f1d7a6e5467d773de16be310f802110000000459dad3f5000000000000000000

1 output(s) for total of 0.615610000000 dcy

stealth address amount amount idx
00: 35f22b18ed0d0ee4aff89b9ce98e7ae68022c079f0206e1ab92a7f0c98db5916 0.615610000000 1483152 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": 1019249, "vin": [ { "gen": { "height": 1019239 } } ], "vout": [ { "amount": 615610000, "target": { "key": "35f22b18ed0d0ee4aff89b9ce98e7ae68022c079f0206e1ab92a7f0c98db5916" } } ], "extra": [ 1, 136, 147, 160, 245, 25, 25, 217, 160, 105, 1, 131, 240, 21, 201, 63, 49, 132, 112, 57, 241, 215, 166, 229, 70, 125, 119, 61, 225, 107, 227, 16, 248, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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