Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f43ca344fc456df064ee3cf1159c3fb97134de9e22e3a740a510f655d2611788

Tx prefix hash: 594cbad68acdc472d9b98c98e52f398aa8edacdd825365b1ed9b3dc124c6f4a4
Tx public key: 2611386ec273927c78995512e2dea0babb9d2cbb5590a2c152efd69d5aed11d6
Timestamp: 1735421193 Timestamp [UCT]: 2024-12-28 21:26:33 Age [y:d:h:m:s]: 00:310:10:22:50
Block: 1185272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219376 RingCT/type: yes/0
Extra: 012611386ec273927c78995512e2dea0babb9d2cbb5590a2c152efd69d5aed11d60211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9cda98280c3f535766682964a483e4867d5bec6a30e3a1e2f58f5bf026d25fd3 0.600000000000 1671739 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": 1185282, "vin": [ { "gen": { "height": 1185272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9cda98280c3f535766682964a483e4867d5bec6a30e3a1e2f58f5bf026d25fd3" } } ], "extra": [ 1, 38, 17, 56, 110, 194, 115, 146, 124, 120, 153, 85, 18, 226, 222, 160, 186, 187, 157, 44, 187, 85, 144, 162, 193, 82, 239, 214, 157, 90, 237, 17, 214, 2, 17, 0, 0, 0, 8, 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