Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17177e5e9fd7ba025bf932d1df4573d7d96ab67677f06d72e73db4ab072ddbea

Tx prefix hash: 90016d75614f3446649a53cb431a20d2506ae45d2cfb9b6da4cd90c87bb8cf3a
Tx public key: 3f8058e9e050a5f093a2e05a8a35391d6b4eff35a3270add100be7f62de18b60
Timestamp: 1736118338 Timestamp [UCT]: 2025-01-05 23:05:38 Age [y:d:h:m:s]: 00:312:07:36:59
Block: 1191054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220724 RingCT/type: yes/0
Extra: 013f8058e9e050a5f093a2e05a8a35391d6b4eff35a3270add100be7f62de18b6002110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6754a9a140f551861291a3f722b3a63ed5d5180041acb3d9340f201a45a90058 0.600000000000 1677577 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": 1191064, "vin": [ { "gen": { "height": 1191054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6754a9a140f551861291a3f722b3a63ed5d5180041acb3d9340f201a45a90058" } } ], "extra": [ 1, 63, 128, 88, 233, 224, 80, 165, 240, 147, 162, 224, 90, 138, 53, 57, 29, 107, 78, 255, 53, 163, 39, 10, 221, 16, 11, 231, 246, 45, 225, 139, 96, 2, 17, 0, 0, 0, 1, 37, 163, 90, 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