Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fdc567fff4b2c7f735e23a02bf5eef01c1914f01c615e92e586ada0186b7ef2

Tx prefix hash: 1c61d158aad286f5dfdacf6a27cd5c0fb85f09980c25ec0d8c3f00e8f97d1d90
Tx public key: ef1233e625d06210d961d8f324d45d7155872af60bd92361ca9f3b279b99e563
Timestamp: 1724678969 Timestamp [UCT]: 2024-08-26 13:29:29 Age [y:d:h:m:s]: 00:261:08:48:21
Block: 1096339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186700 RingCT/type: yes/0
Extra: 01ef1233e625d06210d961d8f324d45d7155872af60bd92361ca9f3b279b99e563021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0a6e34a4f0e114c68277a3db5be43085531d84b3c55106e8f0dadb852957ed9 0.600000000000 1571528 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": 1096349, "vin": [ { "gen": { "height": 1096339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0a6e34a4f0e114c68277a3db5be43085531d84b3c55106e8f0dadb852957ed9" } } ], "extra": [ 1, 239, 18, 51, 230, 37, 208, 98, 16, 217, 97, 216, 243, 36, 212, 93, 113, 85, 135, 42, 246, 11, 217, 35, 97, 202, 159, 59, 39, 155, 153, 229, 99, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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