Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 438c63a50592568048cfc88ae702724dc265efbe593325e61ebfd3664accd86d

Tx prefix hash: 54099a6a91e75b1ffcc5cd6baf68bca186e0395c938b3d5acae1c91046573334
Tx public key: b7f75b178be4eb722c30d4418a5931779e0a958dd47ea7f45d95c0b5aa364eeb
Timestamp: 1694309197 Timestamp [UCT]: 2023-09-10 01:26:37 Age [y:d:h:m:s]: 01:221:08:53:23
Block: 844745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419333 RingCT/type: yes/0
Extra: 01b7f75b178be4eb722c30d4418a5931779e0a958dd47ea7f45d95c0b5aa364eeb02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.975010312000 dcy

stealth address amount amount idx
00: f8bfbdf9dca2c2f2c442bb768fd712edc585ea4c5cfe23b4ffcb70f09cd5630b 0.975010312000 1298073 of 0

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": 844755, "vin": [ { "gen": { "height": 844745 } } ], "vout": [ { "amount": 975010312, "target": { "key": "f8bfbdf9dca2c2f2c442bb768fd712edc585ea4c5cfe23b4ffcb70f09cd5630b" } } ], "extra": [ 1, 183, 247, 91, 23, 139, 228, 235, 114, 44, 48, 212, 65, 138, 89, 49, 119, 158, 10, 149, 141, 212, 126, 167, 244, 93, 149, 192, 181, 170, 54, 78, 235, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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