Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ff0c21bbb377e7a445beda340d91f7faecdf110f36efaa34a3a59bc6caea3a5

Tx prefix hash: 2a075e8e2804fd2c8f6fa488bf99cba0ea5040f98492c290cc8491fd5ecc1a97
Tx public key: 5ecc3cc4edb195b5728d9a15f95d1a842048107b32e0dac988d0e9c88eb64f0b
Timestamp: 1577025411 Timestamp [UCT]: 2019-12-22 14:36:51 Age [y:d:h:m:s]: 05:069:15:29:23
Block: 29655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1199240 RingCT/type: yes/0
Extra: 015ecc3cc4edb195b5728d9a15f95d1a842048107b32e0dac988d0e9c88eb64f0b02110000000d4943cd9f000000000000000000

1 output(s) for total of 489.487422991000 dcy

stealth address amount amount idx
00: e749fbb40c99ab2182b35b30fdc6c02523987adb5fcc9020619c55fd959e6a6e 489.487422991000 48807 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": 29665, "vin": [ { "gen": { "height": 29655 } } ], "vout": [ { "amount": 489487422991, "target": { "key": "e749fbb40c99ab2182b35b30fdc6c02523987adb5fcc9020619c55fd959e6a6e" } } ], "extra": [ 1, 94, 204, 60, 196, 237, 177, 149, 181, 114, 141, 154, 21, 249, 93, 26, 132, 32, 72, 16, 123, 50, 224, 218, 201, 136, 208, 233, 200, 142, 182, 79, 11, 2, 17, 0, 0, 0, 13, 73, 67, 205, 159, 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