Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f1b7b92dbdaf32b039a95c361d36b906bd4c123d215430af406a8cee999d82b

Tx prefix hash: e0cbf38c2cc55579603f30502a4e37972a4952958a37b72705d7a691789ed05d
Tx public key: 78568fad21ab9a0e8cb0ba95bf5c4ac9235dce47ce378f6f09d8db36e7c6be03
Timestamp: 1733539918 Timestamp [UCT]: 2024-12-07 02:51:58 Age [y:d:h:m:s]: 00:112:01:17:03
Block: 1169704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79872 RingCT/type: yes/0
Extra: 0178568fad21ab9a0e8cb0ba95bf5c4ac9235dce47ce378f6f09d8db36e7c6be030211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c4c0536b509924e1e181ab3f131c7c734fe7f3fa94bbf48097f6f763164c772 0.600000000000 1655427 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": 1169714, "vin": [ { "gen": { "height": 1169704 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c4c0536b509924e1e181ab3f131c7c734fe7f3fa94bbf48097f6f763164c772" } } ], "extra": [ 1, 120, 86, 143, 173, 33, 171, 154, 14, 140, 176, 186, 149, 191, 92, 74, 201, 35, 93, 206, 71, 206, 55, 143, 111, 9, 216, 219, 54, 231, 198, 190, 3, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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