Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8b10eb7fd82ed233d61fd45b0b6d3befbcebf747362414a67a7755af663dedb

Tx prefix hash: aa84312f2650eb3432c91dfb3e2189b10844b04794c26598038db3097f69c3c7
Tx public key: 1ec5da247bce04303dc982d4fc317eedde30102b2e07c18bec1b3b3e6be81799
Timestamp: 1732040589 Timestamp [UCT]: 2024-11-19 18:23:09 Age [y:d:h:m:s]: 00:176:07:02:49
Block: 1157291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125833 RingCT/type: yes/0
Extra: 011ec5da247bce04303dc982d4fc317eedde30102b2e07c18bec1b3b3e6be81799021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2d86faa030387c4ad3dca146c66ea2c4c45b74b3b837c1ab6f6dd4bf2b7d04a 0.600000000000 1642914 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": 1157301, "vin": [ { "gen": { "height": 1157291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2d86faa030387c4ad3dca146c66ea2c4c45b74b3b837c1ab6f6dd4bf2b7d04a" } } ], "extra": [ 1, 30, 197, 218, 36, 123, 206, 4, 48, 61, 201, 130, 212, 252, 49, 126, 237, 222, 48, 16, 43, 46, 7, 193, 139, 236, 27, 59, 62, 107, 232, 23, 153, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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