Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db39ff7deb36f3671f8a358ca12b2577dd10f9e1cae8364cafadde34b7865218

Tx prefix hash: a5d5ffd26636b66f5f2f0e5101e5e26af14865964620ed57d44b440e1b53cc60
Tx public key: 7954c6ad72bdd816f6a30224e8088231d50fb400439ebe5f7f3584a95a8e5468
Timestamp: 1707541629 Timestamp [UCT]: 2024-02-10 05:07:09 Age [y:d:h:m:s]: 01:054:06:23:47
Block: 954258 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299835 RingCT/type: yes/0
Extra: 017954c6ad72bdd816f6a30224e8088231d50fb400439ebe5f7f3584a95a8e546802110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f31ea9ce6a8f9bfd570938cadb6b42c627be1c076cf500aa7ab4b1f1d1d49039 0.600000000000 1413536 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": 954268, "vin": [ { "gen": { "height": 954258 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f31ea9ce6a8f9bfd570938cadb6b42c627be1c076cf500aa7ab4b1f1d1d49039" } } ], "extra": [ 1, 121, 84, 198, 173, 114, 189, 216, 22, 246, 163, 2, 36, 232, 8, 130, 49, 213, 15, 180, 0, 67, 158, 190, 95, 127, 53, 132, 169, 90, 142, 84, 104, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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