Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e548216c1762aa17d41bdcdfd45780dc32d788ddf5da06e35faa1031bb570355

Tx prefix hash: a7ca9ba10ded40fafe0d06404b13ea305ff035d4b7a90f255b9a5d9e26fe77d9
Tx public key: 4787977befd5a99b5827dd5e1b7c170994698beb7592272e35c5eacefe3dbaa5
Timestamp: 1635289983 Timestamp [UCT]: 2021-10-26 23:13:03 Age [y:d:h:m:s]: 03:139:10:37:32
Block: 361160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 877884 RingCT/type: yes/0
Extra: 014787977befd5a99b5827dd5e1b7c170994698beb7592272e35c5eacefe3dbaa50211000000016e80e2c6000000000000000000

1 output(s) for total of 39.026076399000 dcy

stealth address amount amount idx
00: a1ff4b253485ea2675fa648077c8ad301c7ee0768d712d50ad0080c1ec9d6c35 39.026076399000 734877 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": 361170, "vin": [ { "gen": { "height": 361160 } } ], "vout": [ { "amount": 39026076399, "target": { "key": "a1ff4b253485ea2675fa648077c8ad301c7ee0768d712d50ad0080c1ec9d6c35" } } ], "extra": [ 1, 71, 135, 151, 123, 239, 213, 169, 155, 88, 39, 221, 94, 27, 124, 23, 9, 148, 105, 139, 235, 117, 146, 39, 46, 53, 197, 234, 206, 254, 61, 186, 165, 2, 17, 0, 0, 0, 1, 110, 128, 226, 198, 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