Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a72ca1814d34bb21210df4994ba3d6170fe0edcab2b4917f8a2cff34c95248a5

Tx prefix hash: 512b64bb44566a5a38153bac617aaf0e588fec1fa1cd6c1e62010a35cfa8990b
Tx public key: bade75d519c1113d4f398a59d876b0a7d3082d12a5a28e350a36db49e3b5f384
Timestamp: 1760387292 Timestamp [UCT]: 2025-10-13 20:28:12 Age [y:d:h:m:s]: 00:027:11:09:27
Block: 1389281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19656 RingCT/type: yes/0
Extra: 01bade75d519c1113d4f398a59d876b0a7d3082d12a5a28e350a36db49e3b5f3840211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cbfb0f8ad2acdc2e25a93d3c6ba9a3884b8491dde21b72c43725276f4fd5866 0.600000000000 1877510 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": 1389291, "vin": [ { "gen": { "height": 1389281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cbfb0f8ad2acdc2e25a93d3c6ba9a3884b8491dde21b72c43725276f4fd5866" } } ], "extra": [ 1, 186, 222, 117, 213, 25, 193, 17, 61, 79, 57, 138, 89, 216, 118, 176, 167, 211, 8, 45, 18, 165, 162, 142, 53, 10, 54, 219, 73, 227, 181, 243, 132, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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