Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc4052fea8dcfad5906d411a710f0c628f4fef9ce3084b167fc7a5d3a21d027e

Tx prefix hash: 0f02ae05934168925d9e0ada78981ed8c55a40e290116bd90e6ea5f339e750e2
Tx public key: d6f577c91e412bf4c78f1f8a7b21eb652f0e40a10b9724f2cf47d1f4e631150a
Timestamp: 1631561413 Timestamp [UCT]: 2021-09-13 19:30:13 Age [y:d:h:m:s]: 03:054:04:17:11
Block: 333118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 814294 RingCT/type: yes/0
Extra: 01d6f577c91e412bf4c78f1f8a7b21eb652f0e40a10b9724f2cf47d1f4e631150a02110000000cf60c5d7e000000000000000000

1 output(s) for total of 48.332829919000 dcy

stealth address amount amount idx
00: 39dca75f53c779f69ab97f85f69b55e837515d0b365891f6662ade2518589008 48.332829919000 687561 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": 333128, "vin": [ { "gen": { "height": 333118 } } ], "vout": [ { "amount": 48332829919, "target": { "key": "39dca75f53c779f69ab97f85f69b55e837515d0b365891f6662ade2518589008" } } ], "extra": [ 1, 214, 245, 119, 201, 30, 65, 43, 244, 199, 143, 31, 138, 123, 33, 235, 101, 47, 14, 64, 161, 11, 151, 36, 242, 207, 71, 209, 244, 230, 49, 21, 10, 2, 17, 0, 0, 0, 12, 246, 12, 93, 126, 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