Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dce4514b54fc0afef2ebb8906d572cc3efc537bcfea50866ff8da8ae43e54849

Tx prefix hash: 6b3e9d3bd18172decb3d20126c0b810a63db130175e3ec55d1dedf57f2ffe77c
Tx public key: 97710dc4c8d5b8d60af3db25f3a0b7e0d56e67bdb0c87b81851a82bc164c3c68
Timestamp: 1698450796 Timestamp [UCT]: 2023-10-27 23:53:16 Age [y:d:h:m:s]: 01:172:04:13:05
Block: 879118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384050 RingCT/type: yes/0
Extra: 0197710dc4c8d5b8d60af3db25f3a0b7e0d56e67bdb0c87b81851a82bc164c3c680211000000014b8f5122000000000000000000

1 output(s) for total of 0.750096503000 dcy

stealth address amount amount idx
00: b9f836536a748434a245ee2c821e5d5829140523911ead231c9696d57e3e6d9a 0.750096503000 1334620 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": 879128, "vin": [ { "gen": { "height": 879118 } } ], "vout": [ { "amount": 750096503, "target": { "key": "b9f836536a748434a245ee2c821e5d5829140523911ead231c9696d57e3e6d9a" } } ], "extra": [ 1, 151, 113, 13, 196, 200, 213, 184, 214, 10, 243, 219, 37, 243, 160, 183, 224, 213, 110, 103, 189, 176, 200, 123, 129, 133, 26, 130, 188, 22, 76, 60, 104, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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