Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4a2fd9ab708c2b538c385edfb1bfdaa05852a9dde55bf9175f958fe38de5e74

Tx prefix hash: d93deda4307bf4164e4d30547f8bdd88221717269c2a28388d0bd328f20eed21
Tx public key: 49bb72107abe6af1cf9f9d7db5e2d0c4b1c565ec63d40c12fd8cdd63ce3125d4
Timestamp: 1707882078 Timestamp [UCT]: 2024-02-14 03:41:18 Age [y:d:h:m:s]: 01:046:20:54:11
Block: 957081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294547 RingCT/type: yes/0
Extra: 0149bb72107abe6af1cf9f9d7db5e2d0c4b1c565ec63d40c12fd8cdd63ce3125d402110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67eb0afefb19eaea6eb06acc7234e8540d54c67595b1a6a113e965fc3b945824 0.600000000000 1416395 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": 957091, "vin": [ { "gen": { "height": 957081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67eb0afefb19eaea6eb06acc7234e8540d54c67595b1a6a113e965fc3b945824" } } ], "extra": [ 1, 73, 187, 114, 16, 122, 190, 106, 241, 207, 159, 157, 125, 181, 226, 208, 196, 177, 197, 101, 236, 99, 212, 12, 18, 253, 140, 221, 99, 206, 49, 37, 212, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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