Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d07547acbb2c2b2b5b7f35b8611c0e59b9b92c03cc3d406c38ef74fc377b069

Tx prefix hash: cd18243082ae4177f71051c745e1743531218346e74e64a4b8577cb663a35d6d
Tx public key: f3a4af2e435c67f1a43aa03767f87baaf06f9182cd1dc0e4fe7148cd72437b38
Timestamp: 1717789376 Timestamp [UCT]: 2024-06-07 19:42:56 Age [y:d:h:m:s]: 00:281:03:40:51
Block: 1039228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200948 RingCT/type: yes/0
Extra: 01f3a4af2e435c67f1a43aa03767f87baaf06f9182cd1dc0e4fe7148cd72437b3802110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48dbe35955da5384cd085c5f29725bcfb6dae909164a3b503a8866df2b64c781 0.600000000000 1507855 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": 1039238, "vin": [ { "gen": { "height": 1039228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48dbe35955da5384cd085c5f29725bcfb6dae909164a3b503a8866df2b64c781" } } ], "extra": [ 1, 243, 164, 175, 46, 67, 92, 103, 241, 164, 58, 160, 55, 103, 248, 123, 170, 240, 111, 145, 130, 205, 29, 192, 228, 254, 113, 72, 205, 114, 67, 123, 56, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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