Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11999fadb1d7eed7893504f6aa5062766f8b65bb562d1d363c7f028c1e062cc6

Tx prefix hash: 6f0a74f61f928514bf270532bfd1deb555535251bf60abc0ddabf0d0931f47f6
Tx public key: bc4b02711d32fc40c0b9dd76617625d1902a7c2a822d67197be59f9aef072f10
Timestamp: 1756025132 Timestamp [UCT]: 2025-08-24 08:45:32 Age [y:d:h:m:s]: 00:137:11:26:33
Block: 1353300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98269 RingCT/type: yes/0
Extra: 01bc4b02711d32fc40c0b9dd76617625d1902a7c2a822d67197be59f9aef072f100211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9acb01cc77ee1e7a2f60c5a99a41918ab135cfe12b318ed0deea4bfeab40e65 0.600000000000 1841275 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": 1353310, "vin": [ { "gen": { "height": 1353300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9acb01cc77ee1e7a2f60c5a99a41918ab135cfe12b318ed0deea4bfeab40e65" } } ], "extra": [ 1, 188, 75, 2, 113, 29, 50, 252, 64, 192, 185, 221, 118, 97, 118, 37, 209, 144, 42, 124, 42, 130, 45, 103, 25, 123, 229, 159, 154, 239, 7, 47, 16, 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