Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5d3ae8dd8df91f15f71d1ac8cfeb76f805eca071c957d356917b20b95d03a59

Tx prefix hash: 115046a8ec5ea69ea97519068a032e36760a2b6d8d8a26f9af02c8822f369a8a
Tx public key: 8addfbb18c55a3be09daae8469cf1ea67cdc59955813f43f5885ac571021cd56
Timestamp: 1725094753 Timestamp [UCT]: 2024-08-31 08:59:13 Age [y:d:h:m:s]: 00:218:00:26:24
Block: 1099797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155663 RingCT/type: yes/0
Extra: 018addfbb18c55a3be09daae8469cf1ea67cdc59955813f43f5885ac571021cd5602110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55f964df92cf02e1affaa6ba73632228f616e88456c8cec07b2756dcc1e2fc91 0.600000000000 1575766 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": 1099807, "vin": [ { "gen": { "height": 1099797 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55f964df92cf02e1affaa6ba73632228f616e88456c8cec07b2756dcc1e2fc91" } } ], "extra": [ 1, 138, 221, 251, 177, 140, 85, 163, 190, 9, 218, 174, 132, 105, 207, 30, 166, 124, 220, 89, 149, 88, 19, 244, 63, 88, 133, 172, 87, 16, 33, 205, 86, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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