Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 368cdbd8f41017ccc47bc84dee5ee5966627f50400046270170706400cb5d2b4

Tx prefix hash: 839d92eb034295037d25dd96a74ad037668237429e5a0dcebc2d599b2deaa378
Tx public key: b8ec5b07a1b34e809e0c60f8500b4c4154e023bdc85cc557c16f9875825883e7
Timestamp: 1693327971 Timestamp [UCT]: 2023-08-29 16:52:51 Age [y:d:h:m:s]: 01:135:13:03:02
Block: 836609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358224 RingCT/type: yes/0
Extra: 01b8ec5b07a1b34e809e0c60f8500b4c4154e023bdc85cc557c16f9875825883e702110000000475e3f0e9000000000000000000

1 output(s) for total of 1.037449979000 dcy

stealth address amount amount idx
00: fe1b192d2e381f3f4fdfebbcc65b55cba7eb5c1a3bf68bcce646826cc4241818 1.037449979000 1289201 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": 836619, "vin": [ { "gen": { "height": 836609 } } ], "vout": [ { "amount": 1037449979, "target": { "key": "fe1b192d2e381f3f4fdfebbcc65b55cba7eb5c1a3bf68bcce646826cc4241818" } } ], "extra": [ 1, 184, 236, 91, 7, 161, 179, 78, 128, 158, 12, 96, 248, 80, 11, 76, 65, 84, 224, 35, 189, 200, 92, 197, 87, 193, 111, 152, 117, 130, 88, 131, 231, 2, 17, 0, 0, 0, 4, 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