Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7ce533c0a00c1ac78449d7641a72bb3131100936a584c33d4f7702d280f9608

Tx prefix hash: 360718fa24ab4f17d43025e0008d00a2f06a2192e1d2f359b1ac2a0f58029c03
Tx public key: 7f31848c7bd6f5b6656f30fb74d75699933da3b5248e62c9b1f3c57fb7a5b43c
Timestamp: 1580977216 Timestamp [UCT]: 2020-02-06 08:20:16 Age [y:d:h:m:s]: 05:001:04:36:13
Block: 59706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152947 RingCT/type: yes/0
Extra: 017f31848c7bd6f5b6656f30fb74d75699933da3b5248e62c9b1f3c57fb7a5b43c0211000000037adf42d3000000000000000000

1 output(s) for total of 389.197512274000 dcy

stealth address amount amount idx
00: 7d49996349cea749b88b06f299e34ed3be8345d17db48f52fd5290bd6af3c87a 389.197512274000 110182 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": 59716, "vin": [ { "gen": { "height": 59706 } } ], "vout": [ { "amount": 389197512274, "target": { "key": "7d49996349cea749b88b06f299e34ed3be8345d17db48f52fd5290bd6af3c87a" } } ], "extra": [ 1, 127, 49, 132, 140, 123, 214, 245, 182, 101, 111, 48, 251, 116, 215, 86, 153, 147, 61, 163, 181, 36, 142, 98, 201, 177, 243, 197, 127, 183, 165, 180, 60, 2, 17, 0, 0, 0, 3, 122, 223, 66, 211, 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