Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16a2d02c14828bdf1d2cf64e6d72bba4a0723217f860b0b1e5bd1c8f6be8c15d

Tx prefix hash: 63d1986b2ba2e9c6c7d031fd6ff8fca74417c44d08a3eb37c1c13697ceb00026
Tx public key: c9a99cbe8529e02832b41053fff9c263049c3f3e6ef9651489d6437ef5767590
Timestamp: 1659103728 Timestamp [UCT]: 2022-07-29 14:08:48 Age [y:d:h:m:s]: 02:171:23:40:27
Block: 554294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 644344 RingCT/type: yes/0
Extra: 01c9a99cbe8529e02832b41053fff9c263049c3f3e6ef9651489d6437ef576759002110000001f6570b1ef000000000000000000

1 output(s) for total of 8.941162863000 dcy

stealth address amount amount idx
00: e05fe82e3d4d51603b9b4011c2271e50aae884c330ac97b5e1f10e1911b56c2d 8.941162863000 986142 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": 554304, "vin": [ { "gen": { "height": 554294 } } ], "vout": [ { "amount": 8941162863, "target": { "key": "e05fe82e3d4d51603b9b4011c2271e50aae884c330ac97b5e1f10e1911b56c2d" } } ], "extra": [ 1, 201, 169, 156, 190, 133, 41, 224, 40, 50, 180, 16, 83, 255, 249, 194, 99, 4, 156, 63, 62, 110, 249, 101, 20, 137, 214, 67, 126, 245, 118, 117, 144, 2, 17, 0, 0, 0, 31, 101, 112, 177, 239, 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