Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f971104cdace7568772c12065d9f13fbffb1e2d2737f68e207a2fca26329539

Tx prefix hash: 94ab754892a2a3a057a9ead4153870e234bfae50eeb7554d1e71fbfba3f7f062
Tx public key: 24a9cb0d909ac650a8c2d2946765e612f2f6a2c3cbab358e879477b43002310c
Timestamp: 1674168223 Timestamp [UCT]: 2023-01-19 22:43:43 Age [y:d:h:m:s]: 02:001:09:36:41
Block: 678454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522832 RingCT/type: yes/0
Extra: 0124a9cb0d909ac650a8c2d2946765e612f2f6a2c3cbab358e879477b43002310c02110000000152542ceb000000000000000000

1 output(s) for total of 3.467370127000 dcy

stealth address amount amount idx
00: ed1c237560f63d912419897cdf805615c21b036d06623ca5c8bc6e0272ac6135 3.467370127000 1120337 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": 678464, "vin": [ { "gen": { "height": 678454 } } ], "vout": [ { "amount": 3467370127, "target": { "key": "ed1c237560f63d912419897cdf805615c21b036d06623ca5c8bc6e0272ac6135" } } ], "extra": [ 1, 36, 169, 203, 13, 144, 154, 198, 80, 168, 194, 210, 148, 103, 101, 230, 18, 242, 246, 162, 195, 203, 171, 53, 142, 135, 148, 119, 180, 48, 2, 49, 12, 2, 17, 0, 0, 0, 1, 82, 84, 44, 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