Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0908045be71beaeb000ee48eac920810b0a12925e3c7dc196d72a608c9119c50

Tx prefix hash: 534dfb5703c38ea483852b3bcc020207fa096a8acd843b72b7a0b6d47ca8067d
Tx public key: bcd0462e3e549e4de8e35503c6c82ef07fcf0430b0a4b051a36131dde8345b55
Timestamp: 1583345782 Timestamp [UCT]: 2020-03-04 18:16:22 Age [y:d:h:m:s]: 04:303:16:05:38
Block: 76244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1111563 RingCT/type: yes/0
Extra: 01bcd0462e3e549e4de8e35503c6c82ef07fcf0430b0a4b051a36131dde8345b550211000000380aca7173000000000000000000

1 output(s) for total of 343.062124731000 dcy

stealth address amount amount idx
00: 279422c4a7e7fff6a0080f8fc676510bd0617dbd38b2e9922bf7528fadb8cf24 343.062124731000 140480 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": 76254, "vin": [ { "gen": { "height": 76244 } } ], "vout": [ { "amount": 343062124731, "target": { "key": "279422c4a7e7fff6a0080f8fc676510bd0617dbd38b2e9922bf7528fadb8cf24" } } ], "extra": [ 1, 188, 208, 70, 46, 62, 84, 158, 77, 232, 227, 85, 3, 198, 200, 46, 240, 127, 207, 4, 48, 176, 164, 176, 81, 163, 97, 49, 221, 232, 52, 91, 85, 2, 17, 0, 0, 0, 56, 10, 202, 113, 115, 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