Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f625c066b34b01f56e1c4b2ad9055a59a35ae6451f0f58416f03b039f7e8b8c5

Tx prefix hash: 676a039d0184fbc81894eff13bfa1fa189e8821bd280734c1e1bf517ad3ad838
Tx public key: 32a125aab686a91cf5d5aca31a155417f2f6544de8bbc835b374e43f4727ef9c
Timestamp: 1686473336 Timestamp [UCT]: 2023-06-11 08:48:56 Age [y:d:h:m:s]: 01:318:11:53:06
Block: 779867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488813 RingCT/type: yes/0
Extra: 0132a125aab686a91cf5d5aca31a155417f2f6544de8bbc835b374e43f4727ef9c02110000000275e3f0e9000000000000000000

1 output(s) for total of 1.599473504000 dcy

stealth address amount amount idx
00: e39b28a6587f07c7633962673a278f48174b1b19e1f101e5bcf601e38001b8b7 1.599473504000 1229552 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": 779877, "vin": [ { "gen": { "height": 779867 } } ], "vout": [ { "amount": 1599473504, "target": { "key": "e39b28a6587f07c7633962673a278f48174b1b19e1f101e5bcf601e38001b8b7" } } ], "extra": [ 1, 50, 161, 37, 170, 182, 134, 169, 28, 245, 213, 172, 163, 26, 21, 84, 23, 242, 246, 84, 77, 232, 187, 200, 53, 179, 116, 228, 63, 71, 39, 239, 156, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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