Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f749f3e129f68d342d0597a7f24bea3d89b5a5423f1e4fe971c1ca08923b29b

Tx prefix hash: 55ead4d0afbb579cae655d0f58b96d89878714963630dfd3dd336738f2bc05d2
Tx public key: 446a9e45f33ed2d1676f2006494584194cedb9b77999fe6c13af1e90c63bf7fa
Timestamp: 1735647839 Timestamp [UCT]: 2024-12-31 12:23:59 Age [y:d:h:m:s]: 00:324:21:50:59
Block: 1187152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229728 RingCT/type: yes/0
Extra: 01446a9e45f33ed2d1676f2006494584194cedb9b77999fe6c13af1e90c63bf7fa021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a53b9060a4a0fc16f9acb173b8eaa8e03f13dc1bbd99b08aa8b4986e58518542 0.600000000000 1673639 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": 1187162, "vin": [ { "gen": { "height": 1187152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a53b9060a4a0fc16f9acb173b8eaa8e03f13dc1bbd99b08aa8b4986e58518542" } } ], "extra": [ 1, 68, 106, 158, 69, 243, 62, 210, 209, 103, 111, 32, 6, 73, 69, 132, 25, 76, 237, 185, 183, 121, 153, 254, 108, 19, 175, 30, 144, 198, 59, 247, 250, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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