Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e95310913ab67e6e20bd4181f923ba78763b3c31bc9f9ee01b3628bfca523dcf

Tx prefix hash: 7b41e59470aa35565b9cd8cac4ca5ddc39d23aec6bf5dd1389cc8a4efa62cc34
Tx public key: e0c90d3f0f671c335eb491c27d466ae5219ddb46fb01d81f88319ee2636638aa
Timestamp: 1750902256 Timestamp [UCT]: 2025-06-26 01:44:16 Age [y:d:h:m:s]: 00:146:01:11:47
Block: 1312877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102360 RingCT/type: yes/0
Extra: 01e0c90d3f0f671c335eb491c27d466ae5219ddb46fb01d81f88319ee2636638aa0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9bfc0defb011f9bfd85a6d66eee6f252a4aef64a587a108e7ece62d15875c03 0.600000000000 1800512 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": 1312887, "vin": [ { "gen": { "height": 1312877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9bfc0defb011f9bfd85a6d66eee6f252a4aef64a587a108e7ece62d15875c03" } } ], "extra": [ 1, 224, 201, 13, 63, 15, 103, 28, 51, 94, 180, 145, 194, 125, 70, 106, 229, 33, 157, 219, 70, 251, 1, 216, 31, 136, 49, 158, 226, 99, 102, 56, 170, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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