Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d406f04d65eb406325de014f1dd27ffe6c3d2185fe440faa7e519007dfe11d7

Tx prefix hash: 7b27010b7842e4db231c7179644a947000191be8d158ccee5618d433891b5d0f
Tx public key: 730aecccd33e3892e55a85c3930e146b886a1f38b3a2412ac5899b2c881859e5
Timestamp: 1735105712 Timestamp [UCT]: 2024-12-25 05:48:32 Age [y:d:h:m:s]: 00:099:14:37:40
Block: 1182674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70965 RingCT/type: yes/0
Extra: 01730aecccd33e3892e55a85c3930e146b886a1f38b3a2412ac5899b2c881859e50211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5bd8978e38b2edb2edcef4003b56d055cb1a5a9a5b6da022029af3b2f2466d72 0.600000000000 1669109 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": 1182684, "vin": [ { "gen": { "height": 1182674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5bd8978e38b2edb2edcef4003b56d055cb1a5a9a5b6da022029af3b2f2466d72" } } ], "extra": [ 1, 115, 10, 236, 204, 211, 62, 56, 146, 229, 90, 133, 195, 147, 14, 20, 107, 136, 106, 31, 56, 179, 162, 65, 42, 197, 137, 155, 44, 136, 24, 89, 229, 2, 17, 0, 0, 0, 6, 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