Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53259489bfb17eaf120ced804b3ff114b10cf527436c4cff21c6dc74b2c875f6

Tx prefix hash: aa5f2557b7f7ea25e63c56969b31690b4b0c12a1cc755d0e0c5aa94d5936fdff
Tx public key: fc30730d28f32a63863e5464cf622a6f374aca4e3c8b845dc11bf338dc82c5e2
Timestamp: 1685449026 Timestamp [UCT]: 2023-05-30 12:17:06 Age [y:d:h:m:s]: 01:167:22:54:56
Block: 771367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381408 RingCT/type: yes/0
Extra: 01fc30730d28f32a63863e5464cf622a6f374aca4e3c8b845dc11bf338dc82c5e202110000000975e3f0e9000000000000000000

1 output(s) for total of 1.706636742000 dcy

stealth address amount amount idx
00: b3c8f838c49f4e592f53e2dd5b8ff51bfed5e855aa3f6c35950f505d4898754f 1.706636742000 1220722 of 0

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": 771377, "vin": [ { "gen": { "height": 771367 } } ], "vout": [ { "amount": 1706636742, "target": { "key": "b3c8f838c49f4e592f53e2dd5b8ff51bfed5e855aa3f6c35950f505d4898754f" } } ], "extra": [ 1, 252, 48, 115, 13, 40, 243, 42, 99, 134, 62, 84, 100, 207, 98, 42, 111, 55, 74, 202, 78, 60, 139, 132, 93, 193, 27, 243, 56, 220, 130, 197, 226, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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