Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14964faee1a266c87b18fe563431fcc984579a9381903116361ae8a91d42ec3d

Tx prefix hash: 633c1d427fdd0822c37061d795738fac7f2ed61cc4c59a5027381b430349e492
Tx public key: 52c5c16a7d809f68b16778bc6f1f1f87eaa784a1fd928ffcad3706796ca403d6
Timestamp: 1710347368 Timestamp [UCT]: 2024-03-13 16:29:28 Age [y:d:h:m:s]: 00:347:00:42:07
Block: 977548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248090 RingCT/type: yes/0
Extra: 0152c5c16a7d809f68b16778bc6f1f1f87eaa784a1fd928ffcad3706796ca403d602110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8124811ce893f915b87e39b3e39fc01716ae9389e5c17e0f6ad9eb2f51e35de7 0.600000000000 1437551 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": 977558, "vin": [ { "gen": { "height": 977548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8124811ce893f915b87e39b3e39fc01716ae9389e5c17e0f6ad9eb2f51e35de7" } } ], "extra": [ 1, 82, 197, 193, 106, 125, 128, 159, 104, 177, 103, 120, 188, 111, 31, 31, 135, 234, 167, 132, 161, 253, 146, 143, 252, 173, 55, 6, 121, 108, 164, 3, 214, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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