Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b57e8686d8f3f3184c43d0662cbbd9c92688aabdf0c228d4232014f7c189764e

Tx prefix hash: 880f633f8e3cff76728fd5a0ee248ad610e2334c494f0d0e5d630beb4214ecc1
Tx public key: eb5d4f9a442f8cd2d7e0604ec370529ddec04fb3fcdcbf1243216018be84ecdd
Timestamp: 1697020810 Timestamp [UCT]: 2023-10-11 10:40:10 Age [y:d:h:m:s]: 01:139:16:24:53
Block: 867250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360835 RingCT/type: yes/0
Extra: 01eb5d4f9a442f8cd2d7e0604ec370529ddec04fb3fcdcbf1243216018be84ecdd02110000000233af99f4000000000000000000

1 output(s) for total of 0.821184548000 dcy

stealth address amount amount idx
00: 81886c520e1761e1145b78b447f6da826bf341a71cf6910d02373f2ac61dc3f6 0.821184548000 1321920 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": 867260, "vin": [ { "gen": { "height": 867250 } } ], "vout": [ { "amount": 821184548, "target": { "key": "81886c520e1761e1145b78b447f6da826bf341a71cf6910d02373f2ac61dc3f6" } } ], "extra": [ 1, 235, 93, 79, 154, 68, 47, 140, 210, 215, 224, 96, 78, 195, 112, 82, 157, 222, 192, 79, 179, 252, 220, 191, 18, 67, 33, 96, 24, 190, 132, 236, 221, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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