Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb6d40d233dc1fa8732a5537c2d81074cc7182c096fd7fa34acba3698322c78a

Tx prefix hash: 825854bb90e4dd2fb7cfbf327ab3d366689f993ec9effe8146a7776fe0f4322f
Tx public key: f979cb6b32a7109ccbd3938da7295a9411d6f79c894d9a38655d484a3267c5ad
Timestamp: 1752904629 Timestamp [UCT]: 2025-07-19 05:57:09 Age [y:d:h:m:s]: 00:169:10:36:47
Block: 1328628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119970 RingCT/type: yes/0
Extra: 01f979cb6b32a7109ccbd3938da7295a9411d6f79c894d9a38655d484a3267c5ad021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea6f726b9d1a00845334dc2e47e6635c176ec5bbdf3866b9b91cbe8d9362b8df 0.600000000000 1816391 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": 1328638, "vin": [ { "gen": { "height": 1328628 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea6f726b9d1a00845334dc2e47e6635c176ec5bbdf3866b9b91cbe8d9362b8df" } } ], "extra": [ 1, 249, 121, 203, 107, 50, 167, 16, 156, 203, 211, 147, 141, 167, 41, 90, 148, 17, 214, 247, 156, 137, 77, 154, 56, 101, 93, 72, 74, 50, 103, 197, 173, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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