Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3afacec59eff6ea5d8458fe548ac6c2a8f3d804fb14dabd35a70e27ce6b31e8

Tx prefix hash: 9d0844fe82980a621abe47bce615eaf2022b119df31403f1162536f923d7b718
Tx public key: 69d3732e3bd1025c7e15eeb6b35d4e9c34262994ba39cc8b4ec88690baee8ab7
Timestamp: 1697418894 Timestamp [UCT]: 2023-10-16 01:14:54 Age [y:d:h:m:s]: 01:140:02:38:40
Block: 870548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361144 RingCT/type: yes/0
Extra: 0169d3732e3bd1025c7e15eeb6b35d4e9c34262994ba39cc8b4ec88690baee8ab7021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.800779821000 dcy

stealth address amount amount idx
00: 94b80e9c1ea942ef58336d8b0f096ce60d2ccc30e88da9d7f515f319f16e72e8 0.800779821000 1325431 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": 870558, "vin": [ { "gen": { "height": 870548 } } ], "vout": [ { "amount": 800779821, "target": { "key": "94b80e9c1ea942ef58336d8b0f096ce60d2ccc30e88da9d7f515f319f16e72e8" } } ], "extra": [ 1, 105, 211, 115, 46, 59, 209, 2, 92, 126, 21, 238, 182, 179, 93, 78, 156, 52, 38, 41, 148, 186, 57, 204, 139, 78, 200, 134, 144, 186, 238, 138, 183, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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