Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a98a1ec9d1a2462e1dee449316d007ab2b57eb7f723a0045f2a4550094697e7

Tx prefix hash: 5439eaf946cac8b5c20bf21fbd55a89ff227e139b3a71ebd2a00ea4d21390157
Tx public key: a52e3a3d8ce57d7dee078e184ed5023d1fdfba8157bdf487aabf15584fa182e7
Timestamp: 1706017295 Timestamp [UCT]: 2024-01-23 13:41:35 Age [y:d:h:m:s]: 01:073:02:38:55
Block: 941603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313351 RingCT/type: yes/0
Extra: 01a52e3a3d8ce57d7dee078e184ed5023d1fdfba8157bdf487aabf15584fa182e702110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8fa32c82d793d9469055d41b64b53970410fef3a7d106650dd322c14ff93ca2a 0.600000000000 1399759 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": 941613, "vin": [ { "gen": { "height": 941603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8fa32c82d793d9469055d41b64b53970410fef3a7d106650dd322c14ff93ca2a" } } ], "extra": [ 1, 165, 46, 58, 61, 140, 229, 125, 125, 238, 7, 142, 24, 78, 213, 2, 61, 31, 223, 186, 129, 87, 189, 244, 135, 170, 191, 21, 88, 79, 161, 130, 231, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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