Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f41a8cd01098feaaaf7fcd8a3cda869ef8ec95a151cf54d682597fa02f9ba65

Tx prefix hash: 4ffb60071aac533e8d16c77ba4a3c4f4ae5f3129418dca37d086406130879473
Tx public key: a1e26b047ad7c8f47d7437270e7133adea4c650c930056bdc0167c0920ecb3fe
Timestamp: 1648512464 Timestamp [UCT]: 2022-03-29 00:07:44 Age [y:d:h:m:s]: 02:287:22:03:56
Block: 468542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 725343 RingCT/type: yes/0
Extra: 01a1e26b047ad7c8f47d7437270e7133adea4c650c930056bdc0167c0920ecb3fe0211000000044a0f5013000000000000000000

1 output(s) for total of 17.199907233000 dcy

stealth address amount amount idx
00: 4f08f1e6540efb40460dc45a9e861ac6fb579f1e35071a95780a5dab0c49a093 17.199907233000 887280 of 0

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": 468552, "vin": [ { "gen": { "height": 468542 } } ], "vout": [ { "amount": 17199907233, "target": { "key": "4f08f1e6540efb40460dc45a9e861ac6fb579f1e35071a95780a5dab0c49a093" } } ], "extra": [ 1, 161, 226, 107, 4, 122, 215, 200, 244, 125, 116, 55, 39, 14, 113, 51, 173, 234, 76, 101, 12, 147, 0, 86, 189, 192, 22, 124, 9, 32, 236, 179, 254, 2, 17, 0, 0, 0, 4, 74, 15, 80, 19, 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