Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b43d7259132890787f6dbabfc7b28e6f8283fb8bc52f915f816314473bb73d2e

Tx prefix hash: fdf9ebe2a06e5b2cdc8ff44bc66a00854343bc6b2a8c765b3580225f96ad6d1c
Tx public key: 5ef1aebb012d2826e36b8798c06a8ed1fb1f688a32daa233cabc971fb609340e
Timestamp: 1718455760 Timestamp [UCT]: 2024-06-15 12:49:20 Age [y:d:h:m:s]: 00:223:01:42:13
Block: 1044769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159572 RingCT/type: yes/0
Extra: 015ef1aebb012d2826e36b8798c06a8ed1fb1f688a32daa233cabc971fb609340e021100000001f53bc1ce000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd26c27209a1cfb1a15af4e20eab8c535d8b9e48686561bc8c1f1f12cafe7643 0.600000000000 1514166 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": 1044779, "vin": [ { "gen": { "height": 1044769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd26c27209a1cfb1a15af4e20eab8c535d8b9e48686561bc8c1f1f12cafe7643" } } ], "extra": [ 1, 94, 241, 174, 187, 1, 45, 40, 38, 227, 107, 135, 152, 192, 106, 142, 209, 251, 31, 104, 138, 50, 218, 162, 51, 202, 188, 151, 31, 182, 9, 52, 14, 2, 17, 0, 0, 0, 1, 245, 59, 193, 206, 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