Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1027f08f3eeb5aefff5d0be007472a8829ed6e1f1f9edcf90e4fe22282287682

Tx prefix hash: 3f12db1a8f6b1d0c779ec7d1ddcdd46c30d77bd3b7bded7530a3402c0a925890
Tx public key: 786ff795cbffc6f909ccb99bd4bd8e7ce05d9515b08157763e11aefa18a58c5e
Timestamp: 1704439729 Timestamp [UCT]: 2024-01-05 07:28:49 Age [y:d:h:m:s]: 01:089:13:00:45
Block: 928529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325111 RingCT/type: yes/0
Extra: 01786ff795cbffc6f909ccb99bd4bd8e7ce05d9515b08157763e11aefa18a58c5e02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7e1446556209e710e97be1b81aa4923134243ad6949c0324acdc9c116264ab6 0.600000000000 1386389 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": 928539, "vin": [ { "gen": { "height": 928529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7e1446556209e710e97be1b81aa4923134243ad6949c0324acdc9c116264ab6" } } ], "extra": [ 1, 120, 111, 247, 149, 203, 255, 198, 249, 9, 204, 185, 155, 212, 189, 142, 124, 224, 93, 149, 21, 176, 129, 87, 118, 62, 17, 174, 250, 24, 165, 140, 94, 2, 17, 0, 0, 0, 7, 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