Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d58d4b999ce4a0d00ca022b4e09c2a60480101232ac2aead204ce3df38f4f5c0

Tx prefix hash: 9d56511bac441c5fe854f038226a6b733b1f144bf89fcc9d0fa3dd22faca4b68
Tx public key: 2254aacb316dcc928f15edbc8beb91ca3d8d65f51c0e943a53a85182d2e0882a
Timestamp: 1752078336 Timestamp [UCT]: 2025-07-09 16:25:36 Age [y:d:h:m:s]: 00:131:05:42:32
Block: 1322053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92321 RingCT/type: yes/0
Extra: 012254aacb316dcc928f15edbc8beb91ca3d8d65f51c0e943a53a85182d2e0882a02110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c18cdfe202db183f75177982072248c02433c6f6606adc65ff28f0e7d731cf5 0.600000000000 1809766 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": 1322063, "vin": [ { "gen": { "height": 1322053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c18cdfe202db183f75177982072248c02433c6f6606adc65ff28f0e7d731cf5" } } ], "extra": [ 1, 34, 84, 170, 203, 49, 109, 204, 146, 143, 21, 237, 188, 139, 235, 145, 202, 61, 141, 101, 245, 28, 14, 148, 58, 83, 168, 81, 130, 210, 224, 136, 42, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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