Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e28362176e011f2acb93c25676d6b5cd281d3c2a520936ab273a941e36a70d40

Tx prefix hash: e1b9cf39a2ebb93032c695f4c8729416dd5d5e82fa27ce18c41972b6b55a5064
Tx public key: 6deb3e7edc02a3c7edccef434889b04e4f73f173571d1b68aa29f4d82de90e22
Timestamp: 1733661829 Timestamp [UCT]: 2024-12-08 12:43:49 Age [y:d:h:m:s]: 00:122:14:41:56
Block: 1170725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87422 RingCT/type: yes/0
Extra: 016deb3e7edc02a3c7edccef434889b04e4f73f173571d1b68aa29f4d82de90e22021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 347ca8fda52556a63779154dac3420b4c4d1c03a27f40e1930550a13d97d0aee 0.600000000000 1656458 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": 1170735, "vin": [ { "gen": { "height": 1170725 } } ], "vout": [ { "amount": 600000000, "target": { "key": "347ca8fda52556a63779154dac3420b4c4d1c03a27f40e1930550a13d97d0aee" } } ], "extra": [ 1, 109, 235, 62, 126, 220, 2, 163, 199, 237, 204, 239, 67, 72, 137, 176, 78, 79, 115, 241, 115, 87, 29, 27, 104, 170, 41, 244, 216, 45, 233, 14, 34, 2, 17, 0, 0, 0, 5, 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