Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3660d0285373e129e813c048c0d14da1dcb84a4126760c1a23ad97b22a1a74e

Tx prefix hash: b85b1172a49ec3ca60e7b641394217194908a14d68b1d9b556cdc010744a7241
Tx public key: a401309de534bfbb56a6f10f3bcac4be1fd62c367d38c5263f3eef4541bac073
Timestamp: 1734419889 Timestamp [UCT]: 2024-12-17 07:18:09 Age [y:d:h:m:s]: 00:113:11:15:27
Block: 1177012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80866 RingCT/type: yes/0
Extra: 01a401309de534bfbb56a6f10f3bcac4be1fd62c367d38c5263f3eef4541bac073021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4faf4f7c53ed410adc3bc25a2a4e6ba2d505335342861061f4d2ff61e1bf6221 0.600000000000 1663373 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": 1177022, "vin": [ { "gen": { "height": 1177012 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4faf4f7c53ed410adc3bc25a2a4e6ba2d505335342861061f4d2ff61e1bf6221" } } ], "extra": [ 1, 164, 1, 48, 157, 229, 52, 191, 187, 86, 166, 241, 15, 59, 202, 196, 190, 31, 214, 44, 54, 125, 56, 197, 38, 63, 62, 239, 69, 65, 186, 192, 115, 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