Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc1f185e1633ea4408be6ad1a34f460bb2f9abaad61666b3a0cf3f4d37384ec4

Tx prefix hash: 005daff38393093936f400806dc3355deb39ced5982f3bb0fe3887362a544817
Tx public key: 6ca0079f9dd3eca3fdf7e11c308ec6442d9bdea9df6f1f74a502a6029d52d45a
Timestamp: 1608924461 Timestamp [UCT]: 2020-12-25 19:27:41 Age [y:d:h:m:s]: 03:328:03:11:11
Block: 169349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 986636 RingCT/type: yes/0
Extra: 016ca0079f9dd3eca3fdf7e11c308ec6442d9bdea9df6f1f74a502a6029d52d45a0211000002de90ce5c0f000000000000000000

1 output(s) for total of 168.607593416000 dcy

stealth address amount amount idx
00: 1348a18902b7ed80e57b3f8e47bbadf5e5526dc66615e4a3c5391d28b41a1cbc 168.607593416000 315962 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": 169359, "vin": [ { "gen": { "height": 169349 } } ], "vout": [ { "amount": 168607593416, "target": { "key": "1348a18902b7ed80e57b3f8e47bbadf5e5526dc66615e4a3c5391d28b41a1cbc" } } ], "extra": [ 1, 108, 160, 7, 159, 157, 211, 236, 163, 253, 247, 225, 28, 48, 142, 198, 68, 45, 155, 222, 169, 223, 111, 31, 116, 165, 2, 166, 2, 157, 82, 212, 90, 2, 17, 0, 0, 2, 222, 144, 206, 92, 15, 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