Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80442fd4efff2b5e0f4ea6b83e221d67a738fd1f8c5c160691aa32e995ded92d

Tx prefix hash: 33eef81ce4301ca71072edfe6fc7f779e117188cee75c7c6df72faeb6f608d2c
Tx public key: 7b752735b241764cc62bb5b3a4a7373ac6a791c1e2c614129f4e5be005304388
Timestamp: 1732830463 Timestamp [UCT]: 2024-11-28 21:47:43 Age [y:d:h:m:s]: 00:202:18:29:12
Block: 1163826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144648 RingCT/type: yes/0
Extra: 017b752735b241764cc62bb5b3a4a7373ac6a791c1e2c614129f4e5be0053043880211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ba69ad2dd4cc83964c1342cf442ed4a9b544632dcd07142fb7a41ae5693a445 0.600000000000 1649495 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": 1163836, "vin": [ { "gen": { "height": 1163826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ba69ad2dd4cc83964c1342cf442ed4a9b544632dcd07142fb7a41ae5693a445" } } ], "extra": [ 1, 123, 117, 39, 53, 178, 65, 118, 76, 198, 43, 181, 179, 164, 167, 55, 58, 198, 167, 145, 193, 226, 198, 20, 18, 159, 78, 91, 224, 5, 48, 67, 136, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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