Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af008a363ae24e1e4304ede2dd5f6dec9b4900dde92e0ef5a62e9f93bfec14a7

Tx prefix hash: c4f02b16cbe312a3af04af79e0457d41475967d6edcfa492e6fd4d09ddfa4015
Tx public key: cf2cfd43da12fad148a7689545f86b7f65e479573073b1d6c4be9a315b7ba63a
Timestamp: 1737048528 Timestamp [UCT]: 2025-01-16 17:28:48 Age [y:d:h:m:s]: 00:059:06:12:42
Block: 1198748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42137 RingCT/type: yes/0
Extra: 01cf2cfd43da12fad148a7689545f86b7f65e479573073b1d6c4be9a315b7ba63a021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf81550f3006aac79be09ea08fd69a0e7de813faa32b7e0e741caf5f5b8665fa 0.600000000000 1685375 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": 1198758, "vin": [ { "gen": { "height": 1198748 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf81550f3006aac79be09ea08fd69a0e7de813faa32b7e0e741caf5f5b8665fa" } } ], "extra": [ 1, 207, 44, 253, 67, 218, 18, 250, 209, 72, 167, 104, 149, 69, 248, 107, 127, 101, 228, 121, 87, 48, 115, 177, 214, 196, 190, 154, 49, 91, 123, 166, 58, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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