Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32a5a4fd6261812e2012a9fae37028e2ea799ab8ab1e1a3aa9e8b89babaf34c9

Tx prefix hash: 7016db84145c1036d3556ee5ca93f4fb5068edf11379585fe4c130eeaf06537b
Tx public key: 239e07189d086b821dc741ce2322d7c8215bb096dd703f49750dc2ca7af0ee85
Timestamp: 1711350220 Timestamp [UCT]: 2024-03-25 07:03:40 Age [y:d:h:m:s]: 01:019:22:58:47
Block: 985867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275232 RingCT/type: yes/0
Extra: 01239e07189d086b821dc741ce2322d7c8215bb096dd703f49750dc2ca7af0ee850211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e958b2e6a1daf8608df95eb49ccc1d4254e599f4511e9e1139c89e5a18f67998 0.600000000000 1446088 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": 985877, "vin": [ { "gen": { "height": 985867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e958b2e6a1daf8608df95eb49ccc1d4254e599f4511e9e1139c89e5a18f67998" } } ], "extra": [ 1, 35, 158, 7, 24, 157, 8, 107, 130, 29, 199, 65, 206, 35, 34, 215, 200, 33, 91, 176, 150, 221, 112, 63, 73, 117, 13, 194, 202, 122, 240, 238, 133, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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