Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f210a3a1584e5f1cf12870eb544673c22c5a237bf906c5da395a62320850f8c4

Tx prefix hash: c133d46b5bb20e3a07adc6d22adfe67a76133950de872f5abcea1516cb415dc5
Tx public key: 67bc64751eb4c66fbd1ff5f061148b268bf36e716a3c827b885f2c48eef896ea
Timestamp: 1706439629 Timestamp [UCT]: 2024-01-28 11:00:29 Age [y:d:h:m:s]: 01:049:01:40:32
Block: 945111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296164 RingCT/type: yes/0
Extra: 0167bc64751eb4c66fbd1ff5f061148b268bf36e716a3c827b885f2c48eef896ea02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d91869e5712631a9d2c9f2086ff9c790c63813e934efe7c66939a8ba0ec7f3cd 0.600000000000 1403421 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": 945121, "vin": [ { "gen": { "height": 945111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d91869e5712631a9d2c9f2086ff9c790c63813e934efe7c66939a8ba0ec7f3cd" } } ], "extra": [ 1, 103, 188, 100, 117, 30, 180, 198, 111, 189, 31, 245, 240, 97, 20, 139, 38, 139, 243, 110, 113, 106, 60, 130, 123, 136, 95, 44, 72, 238, 248, 150, 234, 2, 17, 0, 0, 0, 1, 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