Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1478b9c334ffd1e389aa090e8fc16ca8f86ade93adfd328c894af3602b38c69f

Tx prefix hash: ff81727d212d060a6b4fa0d7b77c8919eefa19fff581342b32964945727295b4
Tx public key: 1ce3d6b1cf839728c4351aef5aa23a1da1f58dc79b3904c9f1225e6958d2476b
Timestamp: 1710845573 Timestamp [UCT]: 2024-03-19 10:52:53 Age [y:d:h:m:s]: 01:002:06:22:51
Block: 981679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262579 RingCT/type: yes/0
Extra: 011ce3d6b1cf839728c4351aef5aa23a1da1f58dc79b3904c9f1225e6958d2476b02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58608f36069ef1de6f1bd5a77cada6e1344000eff9e6c429198dba4e5586b9cf 0.600000000000 1441776 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": 981689, "vin": [ { "gen": { "height": 981679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58608f36069ef1de6f1bd5a77cada6e1344000eff9e6c429198dba4e5586b9cf" } } ], "extra": [ 1, 28, 227, 214, 177, 207, 131, 151, 40, 196, 53, 26, 239, 90, 162, 58, 29, 161, 245, 141, 199, 155, 57, 4, 201, 241, 34, 94, 105, 88, 210, 71, 107, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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