Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b1c7f317bdb5c42f15025719e5d9192f40e00a3576a222f916f2a59abafe93f

Tx prefix hash: 6877d31b7d90366bc9a8fd41b068a15a4af9eda0157a19a25dd178dc99f01c59
Tx public key: e90141ba4a4fa9a0422f687650219d76dcb1b0126727bda41d501fe51d5638d0
Timestamp: 1750175056 Timestamp [UCT]: 2025-06-17 15:44:16 Age [y:d:h:m:s]: 00:156:08:40:06
Block: 1307044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109538 RingCT/type: yes/0
Extra: 01e90141ba4a4fa9a0422f687650219d76dcb1b0126727bda41d501fe51d5638d002110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a3bac7b87ef3e5b4f4a7c7fd26ed648823936dce18f7ee991ab722725a3573e 0.600000000000 1794653 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": 1307054, "vin": [ { "gen": { "height": 1307044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a3bac7b87ef3e5b4f4a7c7fd26ed648823936dce18f7ee991ab722725a3573e" } } ], "extra": [ 1, 233, 1, 65, 186, 74, 79, 169, 160, 66, 47, 104, 118, 80, 33, 157, 118, 220, 177, 176, 18, 103, 39, 189, 164, 29, 80, 31, 229, 29, 86, 56, 208, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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