Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bb9193cd68c09b4d3abbc3082082a402b6af9d4686d64d4faf4f57454e54759

Tx prefix hash: a6b5fab0e5ac5c019cc3406c8e7ceeef6d5afa8e4b6e330f9facce51c078d7ed
Tx public key: 0054698ef8bcdc192444a900e36a076d9e054384401fc6d0c7c2a5574314e0cf
Timestamp: 1702218600 Timestamp [UCT]: 2023-12-10 14:30:00 Age [y:d:h:m:s]: 01:157:05:07:21
Block: 910135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373529 RingCT/type: yes/0
Extra: 010054698ef8bcdc192444a900e36a076d9e054384401fc6d0c7c2a5574314e0cf02110000000433af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66b805a811e4a7faa69bedb6c48c2133cedbf8c4a3d90e72ba54dd3be060f60d 0.600000000000 1367280 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": 910145, "vin": [ { "gen": { "height": 910135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66b805a811e4a7faa69bedb6c48c2133cedbf8c4a3d90e72ba54dd3be060f60d" } } ], "extra": [ 1, 0, 84, 105, 142, 248, 188, 220, 25, 36, 68, 169, 0, 227, 106, 7, 109, 158, 5, 67, 132, 64, 31, 198, 208, 199, 194, 165, 87, 67, 20, 224, 207, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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