Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c785a39828d6005aee18d041645324af5fa4ae015ad087cdacab9237bf9f7e9

Tx prefix hash: 5cf1fd5aeab188eba2db9e1ee50cb01083603c231c1638752d79f93aa6f9a90a
Tx public key: 8c5a8bebe4dcda626216bd2d9b2cfd10cf94507c46109a297652f7475deea952
Timestamp: 1753076958 Timestamp [UCT]: 2025-07-21 05:49:18 Age [y:d:h:m:s]: 00:122:16:38:41
Block: 1330030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86500 RingCT/type: yes/0
Extra: 018c5a8bebe4dcda626216bd2d9b2cfd10cf94507c46109a297652f7475deea95202110000000843846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 364ce164b2ecf6343d7fb614a4fe135c983ee167e7f6581f4eee2b7e1b1446f0 0.600000000000 1817821 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": 1330040, "vin": [ { "gen": { "height": 1330030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "364ce164b2ecf6343d7fb614a4fe135c983ee167e7f6581f4eee2b7e1b1446f0" } } ], "extra": [ 1, 140, 90, 139, 235, 228, 220, 218, 98, 98, 22, 189, 45, 155, 44, 253, 16, 207, 148, 80, 124, 70, 16, 154, 41, 118, 82, 247, 71, 93, 238, 169, 82, 2, 17, 0, 0, 0, 8, 67, 132, 109, 102, 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