Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7971fe2830e379a121afeacd338122545cec9593fbc6806b712e638695fd492

Tx prefix hash: a89bc85c56a8500b1f716f67f71d950c91a2ad7a091421352e6905e0798f6e87
Tx public key: ddb00b20f55b08c88116eeff06a170f03fb1f0e2a1f27e9f647a4c55006d1ab7
Timestamp: 1711403451 Timestamp [UCT]: 2024-03-25 21:50:51 Age [y:d:h:m:s]: 00:230:08:38:51
Block: 986311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164891 RingCT/type: yes/0
Extra: 01ddb00b20f55b08c88116eeff06a170f03fb1f0e2a1f27e9f647a4c55006d1ab702110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d4b4c8e996dc963fdcfde25237d9212c06dfe496bf8ac6ddb9026491b64e545 0.600000000000 1446540 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": 986321, "vin": [ { "gen": { "height": 986311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d4b4c8e996dc963fdcfde25237d9212c06dfe496bf8ac6ddb9026491b64e545" } } ], "extra": [ 1, 221, 176, 11, 32, 245, 91, 8, 200, 129, 22, 238, 255, 6, 161, 112, 240, 63, 177, 240, 226, 161, 242, 126, 159, 100, 122, 76, 85, 0, 109, 26, 183, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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