Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dc2d7ae279af557a95c0b7beb932b592bb5716c9a0da3deacf4a7c8ee96f020

Tx prefix hash: 2d1a4155927f8c3fa72acad7730e7a1790562aad4d6c1c98e8cd6f49e8ac08cb
Tx public key: e463f1a6d56785a096db0031b348c29bcabe9a7941e84f5630d5f2da5fb70549
Timestamp: 1732259713 Timestamp [UCT]: 2024-11-22 07:15:13 Age [y:d:h:m:s]: 00:001:23:32:56
Block: 1159090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1424 RingCT/type: yes/0
Extra: 01e463f1a6d56785a096db0031b348c29bcabe9a7941e84f5630d5f2da5fb70549021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff7d51afff5942f8d83493476592983f8e02ffae1f0056a4a7485e78a9ceef90 0.600000000000 1644721 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": 1159100, "vin": [ { "gen": { "height": 1159090 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff7d51afff5942f8d83493476592983f8e02ffae1f0056a4a7485e78a9ceef90" } } ], "extra": [ 1, 228, 99, 241, 166, 213, 103, 133, 160, 150, 219, 0, 49, 179, 72, 194, 155, 202, 190, 154, 121, 65, 232, 79, 86, 48, 213, 242, 218, 95, 183, 5, 73, 2, 17, 0, 0, 0, 3, 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