Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 210759da5ecec9150b53dbac08777cdb0de4f66e6b93a6a31600b7b1e2a30fdd

Tx prefix hash: b72d4826ac77b8db2a89e0d64517e8e18bb37ce442a11e5bdcc46faec7a273f7
Tx public key: 14d882f67b7e2ae5545f23de7a6b9a857d9174e55dae49517b3d6a5d65e38f0b
Timestamp: 1717570164 Timestamp [UCT]: 2024-06-05 06:49:24 Age [y:d:h:m:s]: 00:291:21:39:20
Block: 1037419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208591 RingCT/type: yes/0
Extra: 0114d882f67b7e2ae5545f23de7a6b9a857d9174e55dae49517b3d6a5d65e38f0b02110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69d74005714ac5a72f1acb13127f4473207001589230f60561c16bde4b1e03f6 0.600000000000 1505950 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": 1037429, "vin": [ { "gen": { "height": 1037419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69d74005714ac5a72f1acb13127f4473207001589230f60561c16bde4b1e03f6" } } ], "extra": [ 1, 20, 216, 130, 246, 123, 126, 42, 229, 84, 95, 35, 222, 122, 107, 154, 133, 125, 145, 116, 229, 93, 174, 73, 81, 123, 61, 106, 93, 101, 227, 143, 11, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 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