Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d0ff13f4279f037c0a5d08dbe5e7680822de45b33436aaae91f633c6af901c2

Tx prefix hash: c56cd44d6bbbaabbd1b5034f2cebb9abefb9ddc832b024e1a4328c1ad3210763
Tx public key: db3c18177477d8ab84a206094901f1d6393adb9d21b8b5269e590942cbef1299
Timestamp: 1721892581 Timestamp [UCT]: 2024-07-25 07:29:41 Age [y:d:h:m:s]: 01:168:10:13:59
Block: 1073237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378967 RingCT/type: yes/0
Extra: 01db3c18177477d8ab84a206094901f1d6393adb9d21b8b5269e590942cbef129902110000000fe914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b71294d9c0f011e2f338e64e1f87a5332ba748d525b24ecdb8c4fc2c75d86da5 0.600000000000 1545736 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": 1073247, "vin": [ { "gen": { "height": 1073237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b71294d9c0f011e2f338e64e1f87a5332ba748d525b24ecdb8c4fc2c75d86da5" } } ], "extra": [ 1, 219, 60, 24, 23, 116, 119, 216, 171, 132, 162, 6, 9, 73, 1, 241, 214, 57, 58, 219, 157, 33, 184, 181, 38, 158, 89, 9, 66, 203, 239, 18, 153, 2, 17, 0, 0, 0, 15, 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